fix: implement exponential backoff to resolve EventStreamError #94
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
We are getting numerous flags from sentry about:
EventStreamError: An error occurred (serviceUnavailableException) when calling the InvokeModelWithResponseStream
We dont want this anymore. Its probably because too many requests are being sent to bedrock, so exponential backoff is a healthy way to try mitigate this error.
Changes proposed in this pull request
Implement exponential backoff. Maybe further in future we should look at other errors to catch (ThrottlingException etc.)
Guidance to review
Check it is a suitable implementation
Relevant links
Things to check